Rendering destination instant messaging personalization items before communicating with destination

ABSTRACT

Perception of a personalization item in an instant messaging communications session may be enabled by perceiving an identifier corresponding to an intended instant message recipient designated by an instant message sender system, accessing personalization items corresponding to the perceived identifier, and making perceivable the personalization items corresponding to the received identifier to the instant messaging sender system for rendering in an instant messaging application running on the instant messaging sender system, where the personalization items are made perceivable prior to communication with the intended instant message recipient.

This application claims priority to and is a continuation of U.S. patentapplication Ser. No. 10/334,027, filed Dec. 31, 2002, and titled“Rendering Destination Instant Messaging Personalization Items BeforeCommunicating With Destination,” which claims priority under 35 USC§119(e) to U.S. Provisional Application No. 60/384,147, filed May 31,2002, and U.S. Provisional Application No. 60/416,902, filed Oct. 9,2002, and is a continuation-in-part of U.S. application Ser. No.10/305,015, filed Nov. 27, 2002, all of which are incorporated byreference.

TECHNICAL FIELD

This description relates to instant messaging communications and moreparticularly to personalization of instant messaging communications foran instant message sender.

BACKGROUND

Online service providers facilitate access to information and servicesby providing interactive User Interfaces (UIs) that help users navigateto desired resources. For example, in the case of a system forcommunicating using instant messages (IMs), a UI allows an IM sender toinvoke actions, such as establishing a communications link, through theselection of screen objects such as icons, windows, and drop-down menus.The design of a UI has a significant impact on an IM sender's onlineexperience. In particular, the icons, the windows, and the menus of a UImay be arranged to enable an IM sender to locate information andservices quickly and easily.

SUMMARY

In one general aspect, perception of a personalization item in aninstant messaging communications session may be enabled by perceiving anidentifier corresponding to an intended instant message recipientdesignated by an instant message sender system, accessingpersonalization items corresponding to the perceived identifier, andmaking perceivable the personalization items corresponding to thereceived identifier to the instant messaging sender system for renderingin an instant messaging application running on the instant messagingsender system, where the personalization items are made perceivableprior to communication with the intended instant message recipient.

Implementations may include one or more of the following features. Forexample, one or more personalization items may be stored.Personalization items may be accessed on a host system, and also may becommunicated from the host system to the instant message sender system.

The personalization items may be made perceivable at times includingprior to communication of an instant message with the intended instantmessage recipient system, before a communications session is establishedwith the intended instant message recipient system, before the instantmessage sender system sends a message to the intended instant messagerecipient system, and before the instant message sender system receivesa message from the intended instant message recipient system.

Perceiving the identifier may include receiving an identity of theintended instant message recipient and accessing an identifierassociated with the individual intended instant message recipient basedupon the received identity. Receiving the identifier may also includereceiving a location of the personalization item, such as, for example,a location on the host system. The identifier may also include an itemtype, a data size, a flag such as a custom item flag, an official itemflag, a banned item flag, and a redirect to different item flag.

The personalization item may include a graphic, such as an icon, asound, wallpaper capable of being rendered on an instant messagingapplication user interface, an animation sequence, a video segment, anda customized binary object provided by the intended instant messagerecipient. The personalization item may be provided by a party otherthan the intended instant message recipient, and may be enabled to berendered in consideration of a payment.

The personalization item may be configured to expire upon the occurrenceof a predetermined event including the passage of a predetermined lengthof time or on passage of a predetermined date or a predetermined numberof uses. If it is determined that the personalization item has expired,access to the personalization item may be disallowed. If it isdetermined that the personalization item has been banned, access to thepersonalization item may be disallowed.

In another general aspect, perception of a personalization item in aninstant messaging communications session may be enabled by rendering, onan instant message sender system, an instant messaging application userinterface for an instant messaging communications session involving atleast an intended instant message recipient and an instant messagesender and rendering, at the instant message sender system, apersonalization item associated with the instant message recipient priorto communication with the intended instant message recipient system.

Implementations may include one or more of the following features. Forexample, the personalization item may be rendered at the instant messagesender system prior to communication of an instant message with theintended instant message recipient system, before a communicationssession is established with the intended instant message recipientsystem, before the instant message sender system sends a message to theintended instant message recipient system, or before the instant messagesender system receives a message from the intended instant messagerecipient system.

The identifier may be associated with the personalization item, thepersonalization item may be obtained from a source other than a messageused to obtain the identifier, and the personalization item may berendered at the instant message sender system. The identifier mayinclude a location of the personalization item. The identifier also mayinclude an item type, a data size, and a flag such as a custom itemflag, an official item flag, a banned item flag, or a redirect todifferent item flag.

Obtaining the identifier may include sending an identity of the intendedinstant message recipient to an instant message host system, where theinstant message host system stores one or more identifiers associatedwith one or more personalization items for the intended instant messagerecipient, and receiving an identifier associated with the individualintended instant message recipient in a message from the instant messagehost system. Obtaining the identifier also may include locating theidentifier at the intended instant message recipient system andretrieving the identifier from a remote data store.

Obtaining the personalization item may include determining whether thepersonalization item associated with the received identifier isavailable at the instant message sender system, retrieving thepersonalization item from the instant message sender system if thepersonalization item is available at the instant message sender system,and requesting the personalization item from a remote source andreceiving the personalization item from the remote source at the instantmessage sender system if the personalization item is not available atthe instant message sender system. The identifier may be received upon achange in a presence state of the intended instant message recipient.

The personalization item may include a graphic, such as an icon, asound, wallpaper capable of being rendered on an instant messagingapplication user interface, an animation sequence, a video segment, anda customized binary object provided by the intended instant messagerecipient. The personalization item may be provided by a party otherthan the intended instant message recipient and may be enabled to berendered in consideration of a payment. The personalization item may beupdated, and may be configured to expire upon the occurrence of apredetermined event, including the passage of a predetermined length oftime or on passage of a predetermined date or a predetermined number ofuses. If it is determined that the personalization item has expired,display of the personalization item may be disallowed. If it isdetermined that the personalization item has been banned, display of thepersonalization item may be disallowed.

Requesting the personalization item may include identifying the remotesource, requesting the personalization item from an instant messaginghost, or requesting the personalization item from a third-party server.The third-party server includes a server authorized as a partner to aninstant messaging host. The personalization item may include any of theitems noted above. The personalization item may be provided by a thirdparty, and may be enabled to be rendered in consideration of a payment.The personalization item also may be configured to expire upon theoccurrence of a predetermined event such as, for example, the passage ofa predetermined length of time, the passage of a predetermined date, ora predetermined number of uses.

Aspects of the IM personalization may be implemented by an apparatusand/or by a computer program stored on a computer readable medium. Thecomputer readable medium may comprise a disc, a client device, a hostdevice, and/or a propagated signal. In addition, aspects of the IMpersonalization may be implemented in a client/host context or in astandalone or offline client device. The IM personalization items may berendered in a client/host context and may be accessed or updated througha remote device in a client/host environment. The IM personalizationitems also may be rendered by the standalone/offline device and may beaccessed or updated through a remote device in a non-client/hostenvironment such as, for example, a LAN server serving an end user or amainframe serving a terminal device.

Other features will be apparent from the following description,including the drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1-4 are block diagrams of an exemplary communications system.

FIGS. 5 and 10 are flow charts of exemplary processes that may beimplemented by systems such as those of FIGS. 1-4.

FIGS. 6-9 are illustrations of different graphical user interfaces thatmay be implemented by systems such as those of FIGS. 1-4 when executingprocesses such as those of FIGS. 5 and 10 and 11 and 12.

FIGS. 11 and 12 are flow charts of exemplary processes that may beimplemented by systems such as those of FIGS. 1-4.

Like reference symbols in the various drawings indicate like elements.For brevity, several elements in the figures described below arerepresented as monolithic entities. However, as would be understood byone skilled in the art, these elements each may include numerousinterconnected computers and components designed to perform a set ofspecified operations and/or may be dedicated to a particular geographicregion.

DETAILED DESCRIPTION

It is possible, through the systems and techniques described herein, tomake personalization items of an intended IM recipient perceivable to anIM sender in a communications interface of the IM sender (1) immediatelyupon opening the interface, (2) before sending a message or othercommunication to the IM recipient, and/or (3) before receipt of amessage or other communication from the IM recipient. As such,immediately upon opening a communication interface and identifying apotential message recipient, an IM sender may perceive a personalizationitem established for or selected by that potential message recipient,which personalization items may not otherwise be made available to theIM sender until communications are sent or received with respect to thatpotential message recipient.

Personalization items may represent a user or a characteristic of theintended IM recipient, and may include user-selectable binary objects.For example, personalization items include images, such as wallpaper,that are rendered in a location having a contextual placement on a userinterface. The contextual placement typically indicates an associationwith the user represented by the wallpaper. For example, the wallpapermay be rendered in an area where messages from the IM recipient are tobe displayed, or as a chrome (i.e., border) around a dialog area on auser interface. Personalization items also may include icons such asbuddy icons and mini-buddy icons, sounds, animation, video clips, andemoticons (e.g., smileys). Personalization items for the intendedrecipient may be known or unknown to the IM sender, and they may or maynot be stored at the IM sender system or be otherwise associated withthat IM sender prior to the communication session in which they aredisplayed using the systems and techniques described herein.

One or more personalization items of an intended IM recipient may berendered at the IM sender system. An identifier corresponding to one ormore personalization items of the IM recipient is obtained by the IMsender. For instance, an identifier may identify a particularpersonalization item, a group of personalization items, or a user nameor other identity may be mapped to one or more personalization items orgroups.

The IM sender system may use the identifier to identify one or morepersonalization items associated with the IM recipient, and to locateperceivable content corresponding to the identifier. For instance, anidentifier may be used as a basis for determining if one or morecorresponding personalization items are available locally at the IMsender system, and, if so, the identifier may be used to retrieve thecorresponding personalization item(s). If the personalization item(s)are not available locally at the IM sender system, the IM sender systemmay use the identifier as a basis for generating one or more requestsfor the personalization item(s) from another location, such as an IMhost system or another remotely-accessible data store such as the IMrecipient system, or a remote or third-party server (e.g., a serveraccessible through the Internet).

Identifiers may be retrieved before, during, or after receipt of aninstant message or other communication from the IM recipient. Forexample, the identifiers may be retrieved upon the opening of acommunications user interface (UI) by the IM sender or after opening ofthe UI but before receipt of an instant message or other communicationfrom the IM recipient.

The IM sender system may retrieve the identifiers from a remote locationsuch as those noted above. The identifiers may be stored at the remotelocation and associated with a screen name or other user identity of theIM recipient. The IM sender system may send the screen name or otheruser identity of the IM recipient to the remote location where it isthen associated with the corresponding identifiers of the IM recipient,and the IM sender system may receive the corresponding identifiers fromthe remote location. For instance, the IM host may store identifiersassociated with the screen name of an IM recipient. The IM sender systempasses the screen name of the IM recipient to the IM host, and the IMhost returns the identifiers associated with the passed screen name tothe IM sender system. In another implementation, a remotely accessibledata store may retrieve and send the personalization items themselves tothe IM sender rather than sending the identifiers.

In another example, the IM sender system may locally store theidentifiers in association with a screen name or other user identity ofthe IM recipient. The IM sender system may then retrieve thelocally-stored identifiers based on the screen name or other useridentity of the IM recipient. In another implementation, the IM sendersystem may retrieve the personalization items themselves rather than theidentifiers.

Personalization items may be made available to the IM sender systembased on a selecting process. The personalization items to be madeperceivable to the IM sender may be selected manually by the IMrecipient or may be automatically selected for the IM recipient.Identifiers for selected personalization items may be associated with ascreen name or other identifying information for the IM recipient. Forexample, the identifiers associated with the screen name of a potentialIM recipient may be stored locally at the IM sender system, or the IMsender system may retrieve such identifiers from a remotely-accessibledata store such as the IM host system, the IM recipient system, or thosenoted above.

Personalization items of the IM recipient may be rendered to the IMsender before correspondence is initiated or communications areestablished by the recipient and without previously having received anIM message from the IM recipient. Once the IM sender system locates orreceives the one or more personalization items associated with aintended destination recipient, the IM sender system renders the one ormore personalization items for perception by the IM sender. Also, thepersonalization items of the IM sender may be rendered to the IMrecipient in the manner described for rendering the personalizationitems of the IM recipient to the IM sender.

Typically, a personalization item is rendered upon the occurrence of oneor more particular events. For example, a customized sound and/or apersonalized icon or wallpaper selected by an IM recipient may be madeperceivable to an IM sender when the IM sender initiates an IMcommunications session with the IM recipient by, for example, opening anIM communications window. As an example, a particular sound may beplayed or an icon may be displayed at the IM sender system when changesare experienced in presence or state of the IM recipient with whom theycommunicate changes (e.g., when the IM recipient or other IM participantlogs on, logs off, becomes inactive, or enables or disables the IMsender's ability to detect the IM recipient's presence).

In one implementation, the IM sender may not change the personalizationitems of an IM recipient. An IM recipient may choose to have differentpersonalization items displayed for different IM senders. Once apersonalization item is designated by an IM recipient, thepersonalization item is typically made available for perception by theIM sender automatically. The personalization items may also be selectedautomatically for an IM recipient based upon a characteristic of the IMsender.

Typically, IM communications involve an instantaneous or nearlyinstantaneous communication between two users, where each user is ableto transmit, receive and display communicated information. Additionally,although IM communications may occur in the absence of online presenceinformation, IM communications generally involve the display andperception of online presence information regarding other selected users(“buddies”). IM communications may be machine-to-machine communicationsthat occur without intervention by or communication through an instantmessaging server after a communication session is established orauthentication is performed. Examples of IM communications exist overAIM (America Online Instant Messenger), AOL (America Online) Buddy Listand Instant Messages, Yahoo Messenger, MSN Messenger, and ICQ, amongothers. Although discussed below primarily with respect to IMapplications, other implementations are contemplated for providingsimilar functionality in platforms and online applications such as chat,e-mail, and streaming media applications.

For illustrative purposes, FIGS. 1 and 2 show an example of acommunications system for implementing techniques for transferringelectronic data.

Referring to FIG. 1, a communications system 100 is capable ofdelivering and exchanging data between an IM sender system 105 and ahost system 110 through a communications link 115. The IM sender system105 typically includes one or more client devices 120 and/or clientcontrollers 125, and the host system 110 typically includes one or morehost devices 135 and/or host controllers 140. For example, the IM sendersystem 105 or the host system 110 may include one or moregeneral-purpose computers (e.g., personal computers), one or morespecial-purpose computers (e.g., devices specifically programmed tocommunicate with each other and/or the IM sender system 105 or the hostsystem 110), or a combination of one or more general-purpose computersand one or more special-purpose computers. The IM sender system 105 andthe host system 110 may be arranged to operate within or in concert withone or more other systems, such as, for example, one or more LANs(“Local Area Networks”) and/or one or more WANs (“Wide Area Networks”).

The client device 120 and the host device 135 are generally capable ofexecuting instructions under the command of, respectively, a clientcontroller 125 and a host controller 140. The client device 120 and thehost device 135 are connected to, respectively, the client controller125 and the host controller 140 by, respectively, wired or wireless datapathways 130 and 145, which are capable of delivering data.

The client device 120, the client controller 125, the host device 135,and the host controller 140 typically each include one or more hardwarecomponents and/or software components. An example of a client device 120or a host device 135 is a general-purpose computer (e.g., a personalcomputer) or software on such a computer capable of responding to andexecuting instructions in a defined manner. Other examples include aspecial-purpose computer, a workstation, a server, a device, acomponent, other physical or virtual equipment or some combination ofthese capable of responding to and executing instructions. The clientdevice 120 and the host device 135 may include devices that are capableof establishing peer-to-peer communications.

An example of client controller 125 or host controller 140 is a softwareapplication loaded on the client device 120 or the host device 135 forcommanding and directing communications enabled by the client device 120or the host device 135. Other examples include a program, a piece ofcode, an instruction, a device, a computer, a computer system, or acombination of these for independently or collectively instructing theclient device 120 or the host device 135 to interact and operate asdescribed. The client controller 125 and the host controller 140 may beembodied permanently or temporarily in any type of machine, component,physical or virtual equipment, storage medium, or propagated signalcapable of providing instructions to the client device 120 and the hostdevice 135.

The communications link 115 typically includes a delivery network 160that provides direct or indirect communication between the IM sendersystem 105 and the host system 110, irrespective of physical separation.Examples of a delivery network 160 include the Internet, the World WideWeb, WANs, LANs, analog or digital wired and wireless telephone networks(e.g., Public Switched Telephone Network (PSTN), Integrated ServicesDigital Network (ISDN), and Digital Subscriber Line (xDSL)), radio,television, cable, or satellite systems, and other delivery mechanismsfor carrying data. The communications link 115 may include communicationpathways 150 and 155 that enable communications through the one or moredelivery networks 160 described above. Each of the communicationpathways 150 and 155 may include, for example, a wired, wireless, cableor satellite communication pathway.

FIG. 2 illustrates a communications system 200 including an IM sendersystem 105 communicating with a host system 110 through a communicationslink 115.

The IM sender system 105 includes a client device 120 that typicallyincludes a general-purpose computer 270 having an internal or externalmemory 272 for storing data and programs such as an operating system 274(e.g., DOS, Windows™, Windows 95™, Windows 98™, Windows 2000™, WindowsMe™, Windows XP™, Windows NT™, OS/2, or Linux) and one or moreapplication programs. Examples of application programs include authoringapplications 276 (e.g., word processing programs, database programs,spreadsheet programs, or graphics programs) capable of generatingdocuments or other electronic content; client applications 278 (e.g.,America Online (AOL) client, CompuServe client, AOL Instant Messenger(AIM) client, interactive television (ITV) client, Internet ServiceProvider (ISP) client, or instant messaging (IM) client) capable ofcommunicating with other computer users, accessing various computerresources, and viewing, creating, or otherwise manipulating electroniccontent; and browser applications 280 (e.g., Netscape's Navigator orMicrosoft's Internet Explorer) capable of rendering standard Internetcontent and other content formatted according to standard protocols suchas the Hypertext Transfer Protocol (HTTP).

One or more of the application programs may be installed on the internalor external storage 272 of the general-purpose computer 270.Alternatively, in another implementation, the client controller 125 mayaccess application programs externally stored in and/or performed by oneor more device(s) external to the general-purpose computer 270.

The general-purpose computer 270 also includes a central processing unit282 (CPU) for executing instructions in response to commands from theclient controller 125, and a communication device 284 for sending andreceiving data. One example of the communication device 284 is a modem.Other examples include a transceiver, a set-top box, a communicationcard, a satellite dish, an antenna, a network adapter, or some othermechanism capable of transmitting and receiving data over thecommunications link 115 through a wired or wireless data pathway 150.The general-purpose computer 270 optionally includes a television (“TV”)tuner 286 for receiving television programming in the form of broadcast,satellite, and/or cable TV signals. The TV tuner 286 permits the clientdevice 120 to selectively and/or simultaneously display network contentreceived by communications device 284 and TV programming contentreceived by the TV tuner 286.

The general-purpose computer 270 may include an input/output interface288 that enables wired or wireless connection to various peripheraldevices 290. Examples of peripheral devices 290 include, but are notlimited to, a mouse 291, a mobile phone 292, a personal digitalassistant (PDA) 293, an MP3 player (not shown), a keyboard 294, adisplay monitor 295 with or without a touch screen input, a TV remotecontrol 296 for receiving information from and rendering information tousers, and an audiovisual input device 298.

Although FIG. 2 illustrates devices such as a mobile telephone 292, aPDA 293, and a TV remote control 296 as being peripheral with respect tothe general-purpose computer 270, in another implementation, suchdevices may themselves include the functionality of the general-purposecomputer 270 and operate as the client device 120. For example, themobile phone 292 or the PDA 293 may include computing and networkingcapabilities and function as a client device 120 by accessing thedelivery network 160 and communicating with the host system 110.Furthermore, the IM sender system 105 may include one, some or all ofthe components and devices described above.

FIG. 3 illustrates a communications system 300 including an IM sendersystem 105 communicating with an IM recipient system 305 and an IM hostsystem 310 through a communication link 115. Such a communicationssystem may be used by users of IM service providers, such as, forexample, AIM, ICQ, Yahoo Messenger, and Microsoft Messenger.

In one implementation, the IM host system 310 may have characteristicssimilar to those described above with respect to the host system 110,the IM recipient system 305 may have characteristics similar to thosedescribed above with respect to the IM sender system 105, and the IMsender system 105 and the IM recipient system 305 may includecommunication software to enable users of the client systems to accessthe IM host system 310.

The IM host system 310 may support IM services irrespective of an IMsender's network or Internet access. Thus, the IM host system 310 mayallow users to send and receive IMs, regardless of whether they haveaccess to any particular ISP. The IM host system 310 also may supportassociated services, such as administrative matters, advertising,directory services, chat, and interest groups related to the IM. The IMhost system 310 has an architecture that enables the devices (e.g.,servers) within the IM host system 310 to communicate with each other.To transfer data, the IM host system 310 employs one or more standard orexclusive IM protocols.

To access the IM host system 310 to begin an IM session in theimplementation of FIG. 3, the IM sender system 105 establishes aconnection to the IM host system 310. Once a connection to the IM hostsystem 310 has been established, the IM sender system 105 may directlyor indirectly transmit data to and access content from the IM hostsystem 310. By accessing the IM host system, an IM sender can use the IMclient application to view whether particular users (“buddies”) areonline, exchange IMs with particular buddies, participate in group chatrooms, trade files such as pictures, invitations or documents, findother buddies with similar interests, get customized information such asnews and stock quotes, and search the Web. IM recipient system 305 maybe similarly manipulated to establish contemporaneous connection with IMhost system 310.

Once connectivity is established, an IM sender who is using IM sendersystem 105 may view whether an IM recipient using IM recipient system305 is online, and typically may view whether the IM recipient is ableto receive IMs. If the IM recipient is online, the IM sender mayexchange IMs with the IM recipient.

In one implementation, the IMs sent between IM sender system 105 and IMrecipient system 305 are routed through IM host system 310. In anotherimplementation, the IMs sent between IM sender system 105 and IMrecipient system 305 are routed through a third party server (notshown), and, in some cases, are also routed through IM host system 310.In yet another implementation, the IMs are sent directly between IMsender system 105 and IM recipient system 305.

FIG. 4 illustrates a communications system 400 including an IM sendersystem 105 communicating with an IM recipient system 305 and an IM hostsystem 310 through a communication link 115. System 400 illustrates apossible implementation of the communications system 300 of FIG. 3.

In system 400, the IM host system 310 includes a login server 470 forenabling access by users and routing communications between the IMsender system 105 and other elements of the IM host system 310. The IMhost system 310 also includes an IM server 490. To enable access to andfacilitate interactions with the IM host system 310, the IM sendersystem 105 and the IM recipient system 305 may include communicationsoftware, such as for example, an OSP client application and/or an IMclient application.

As described with respect to FIG. 3, the IM host system 310 may supportIM services irrespective of an IM sender's network or Internet access.Thus, the IM host system 310 may allow users to send and receive IMs,regardless of whether they have access to any particular ISP. The IMhost system 310 also may support associated services, such asadministrative matters, advertising, directory services, chat, andinterest groups related to the IM. The IM host system 310 has anarchitecture that enables the devices (e.g., servers) within the IM hostsystem 310 to communicate with each other. To transfer data, the IM hostsystem 310 employs one or more standard or exclusive IM protocols.

In one implementation, the IM sender system 105 establishes a connectionto the login server 470 in order to access the IM host system 310 andbegin an IM session. The login server 470 typically determines whetherthe particular IM sender is authorized to access the IM host system 310by verifying the IM sender's identification and password. If the IMsender is authorized to access the IM host system 310, the login server470 usually employs a hashing technique on the IM sender's screen nameto identify a particular IM server 490 within the IM host system 310 foruse during the IM sender's session. The login server 470 provides the IMsender (e.g., IM sender system 105) with the IP address of the IM server490, gives the IM sender system 105 an encrypted key, and breaks theconnection. The IM sender system 105 then uses the IP address toestablish a connection to the particular IM server 490 through thecommunications link 115, and obtains access to the IM server 490 usingthe encrypted key. Typically, the IM sender system 105 will be able toestablish an open TCP connection to the IM server 490. The IM recipientsystem 305 establishes a connection to the IM host system 310 in asimilar manner.

In one implementation, the IM sender system 105 may directly orindirectly transmit data to and access content from the IM server 490once a connection to the IM server 490 has been established. Byaccessing the IM server, an IM sender can leverage the IM clientapplication to determine whether particular users (“buddies” orpotential IM recipients) are online, exchange IMs with particularbuddies, participate in group chat rooms, trade files such as pictures,invitations or documents, find other buddies with similar interests, getcustomized news and stock quotes, and search the Web. For example an IMsender who is using IM sender system 105 may view whether a buddy usingIM recipient system 305 is online, and if so, may exchange IMs with thatbuddy. In one implementation, the IMs sent between IM sender system 105and IM recipient system 305 are routed through IM host system 310. Inanother implementation, the IMs sent between IM sender system 105 and IMrecipient system 305 are routed through a third party server (not shown)and, in some cases, are also routed through IM host system 310. In yetanother implementation, the IMs are sent directly between IM sendersystem 105 and IM recipient system 305.

In one implementation, the IM host system 310 also includes a userprofile server (not shown) connected to a database (not shown) forstoring large amounts of user profile data. The user profile server maybe used to enter, retrieve, edit, manipulate, or otherwise process userprofile data. In one implementation, an IM recipient's profile dataincludes, for example, the IM recipient's screen name, buddy list,identified interests, and geographic location. The IM recipient mayenter, edit and/or delete profile data using an installed IM clientapplication on the IM recipient system 305 to interact with the userprofile server.

FIGS. 5, 10, 11, and 12 illustrate exemplary procedures 500, 1000, 1100,and 1200 to make a personalization item selected by an intended IMdestination recipient perceivable to the IM sender during an instantmessaging communications session, and, in particular, to render thepersonalization item associated with an intended IM recipient to the IMsender prior to the communication of an instant message with theintended recipient system.

Procedures 500, 1000, 1100, and 1200 generally involve rendering apersonalization item and may be implemented by any type of hardware,software, device, computer, computer system, equipment, component,program, application, code, storage medium, or propagated signal. In oneimplementation, a host 110 may be used in place of the IM host 310.Furthermore, although not shown in FIGS. 5, 10, 11, and 12, the IMsender system 105 and the IM host system 310 may be directly orindirectly interconnected through known or described delivery networks,examples of which are described with respect to network 160.

The procedures 500, 1000, 1100, and 1200 may be implemented in aclient/host context, or a standalone or offline client context. Forexample, while some functions of procedures 500, 1000, 1100, and 1200may be performed entirely by the IM sender system 105, other functionsmay be performed by the IM host system 310 or the collective operationof the IM sender system 105 and the IM host system 310. For instance, apersonalization item may be rendered entirely by the IM sender system105, or the personalization item may be rendered based upon informationprovided to the IM sender system 105 by the IM host system 310.

The personalization item may be rendered by the standalone/offlinedevice and may be accessed or updated through a remote device in anon-client/host environment such as, for example, a LAN server servingan end user or a mainframe serving a terminal device. Thus, theprocedures 500, 1000, 1100, and 1200 described below may be implementedfor any OSP, ISP, browser and/or other software program having agraphical user interface, such as programs for instant messaging, chat,electronic mail and stand-alone browsers.

Referring to FIG. 5, in the procedure 500, the IM sender opens an IMapplication on the IM sender system 105 (step 505). FIG. 6 describes anexemplary interface available to the IM sender, which may be used toopen an IM application on the IM sender system and which will bedescribed below.

Next, an intended destination recipient (hereinafter “IM recipient”) isselected (step 510). FIG. 6 illustrates an exemplary interface availableto the IM sender, which will be described below, and which may be usedto select an intended destination recipient.

Next, an IM user interface (UI) is opened to enable selection ofinformation to be communicated to the intended destination (step 515).FIG. 7 describes an exemplary interface available to the IM sender,which may be used to open an IM user interface, and which will bedescribed below.

Finally, the personalization items associated with the selected IMrecipient are rendered in the IM UI (step 520). FIGS. 8 and 9 describeexemplary interfaces available to the IM sender which may be used whenrendering the personalization items of the selected IM recipient, andwhich will be described below.

The IM recipient may have chosen a personalization item from a locationincluding the IM recipient system 305, the IM host system 310, oranother host system. When the IM recipient chooses a personalizationitem that is locally stored on the IM recipient system 305, anidentifier may be created for the chosen personalization item based upona hash of the item data. The identifier, when sent to the a remotelocation such as the IM host 310, may be checked to determine if thechosen personalization item is already known to the host system, and ifso, whether the personalization item is designated as, for example, anofficial item. This allows the IM recipient to select personalizationitems from the IM recipient's own client system, but prevents the hostsystem or other remote location from needing to store duplicate copiesof the same items. Also, the host system or other remote location isable to determine if such items are specially designated as, forexample, official items and may be rendered to users who desire to viewonly items so designated.

FIG. 6 illustrates an example of a UI 600 that may be presented to auser of an online service provider. The UI 600 includes a toolbar 602for quickly enabling activation of features such as, for example,reading or writing e-mail, exchanging IM messages with another user,entering chat areas with other users, shopping or accessing theinternet. The toolbar 602 may include one or more general interfaceactionable items 620-660, each of which is configured to enableactivation of an associated user interface. An actionable item may be,for example, a button or a tab. For example, general actionable item 620is configured to enable activation of an IM application and associatedInstant Message (IM) user interface (UI) 670. A buddy list 625 isprovided, and includes a list of other potential IM recipient. As shown,the IM sender is able to initiate and view a communications session withIM recipient “SurfinDiane” 625 a.

FIG. 7 illustrates one example of an IM UI 700 that may be presented toan IM sender of an IM service provider. The UI 700 may be rendered afteropening an IM application. In general, the UI 700 is rendered on the IMsender system 105 using software stored on the IM sender system 105.

The UI 700 includes an IM display area 705 to display the messages 705 aof an active IM session. In the example of FIG. 7, the active IM sessioninvolves a conversation initiated by the IM sender having a screen nameof “ChattingChuck” with the IM sender having a screen name of“SurfinDiane.” An IM compose area 710 may be used to compose a messageto send to the IM sender in the active IM session, and the messagetypically is sent by clicking on the send control button 715 in the UI.A control button 720 may be provided to close the active IM session.

The UI 700 includes personalization items 707 and 709 from the IMrecipient and personalization items 712 and 714 from the IM sender. Inparticular, as shown in FIG. 7, the IM recipient “SurfinDiane” has madeIM wallpaper 707 and a buddy icon 709 perceivable to the IM sender“ChattingChuck.”

Personalization items 707 and 709 of the IM recipient may be madeavailable to the IM sender upon activating UI 700 and without having towait to receive a communication such as an instant message from the IMrecipient. The IM sender system 105 selects the identifierscorresponding to the personalization items 707 and 709 of the IMrecipient. The identifiers may be associated with a screen name or otheridentifying information of the IM recipient. For example, theidentifiers may be associated with the screen name of the IM recipientand stored locally at the IM sender system 105, or the IM sender systemmay retrieve the identifiers associated with the screen name of the IMrecipient from another location such as the IM host system 310 oranother remotely-accessible data store such as the IM recipient system305 or a remote or third-party server.

The IM sender system 105 uses the identifiers to determine if thecorresponding personalization items are available locally at the IMsender system, and if so, the IM sender system retrieves thecorresponding personalization items. If the personalization items arenot available locally at the IM sender system 105, the IM sender systemrequests the personalization items from another location such as an IMhost system 310 or another remotely-accessible data store. Once the IMsender system 105 locates or receives the personalization items of theIM recipient, the IM sender system renders the items on UI 700 forperception by the IM sender.

Examples of IM UIs 600, 700 are shown with respect to FIGS. 6 and 7. Inone implementation, the IM user interface is opened after the IMrecipient is selected. In another implementation, the IM user interfaceis opened before the IM recipient is selected. In yet anotherimplementation, the IM user interface is opened simultaneously with theselection of the IM recipient.

FIG. 8 illustrates yet another example of an IM UI 800 that may bepresented to an IM sender of an IM service provider. One or morepersonalization items may be provided for the IM UI. The personalizationitems may be rendered to the IM sender as described above with respectto FIG. 5.

In the example of FIG. 8, personalization items of an IM recipient“AIMUIGIRL” 805, 810, 820, and 825 may be made perceivable to the IMsender in the manner described above with respect to FIGS. 5, 7, and 10.In particular, the personalization items of the IM recipient to be madeperceivable to the IM sender prior to receipt of a communication fromthe IM recipient include a sidebar image 805, a background image 810, abuddy icon 820, and a sound (not shown). The sidebar image 805 mayinclude images and links to content. The background image 810 mayinclude an image, and typically is a washed out image. The buddy icon820 typically is an image. The sound may be a sound or a sequence ofsounds played to the IM sender.

FIG. 9 is an example of an instant messaging buddy list UI 900 thatenables an IM sender of an instant messaging service to, among otherthings, perceive the presence state of other buddies that the IM senderhas added to a buddy list, and to send instant messages to buddies onthe buddy list. The buddy list rendered to the IM sender may includepersonalization items of an IM recipient such as a buddy list bar 905, abuddy list image 910, a buddy list background image 915, and a buddylist fill pattern 920.

The buddy list bar 905 may contain personalized links 905 a, 905 b, 905c, and 905 d to content and may have a customized appearance. The buddylist image 910 and the buddy list background image 915 may be, forexample, image files. The buddy list background image 915 may have awashed out appearance. The buddy list fill pattern 920 may be a color orpattern background for the buddy list, or may also be an image. Thetransmission of the buddy list personalization items of a selected buddyfor rendering on the IM sender system may occur duringmachine-to-machine communications that are not visible to the user.

As shown, the buddy list 900 includes buddies 925 a, 925 b, 925 c thatthe IM sender has chosen to add to the buddy list. Personalization itemsof a given IM recipient (i.e., a buddy) may be displayed through manualselection by the IM sender, or the personalization items of a given IMrecipient may be selected automatically for the IM sender such as, forexample, when the IM sender activates a UI to send an IM message to aselected IM recipient.

For example, wallpaper or a different personalization item reflective ofsettings established for a selected buddy may be rendered on the buddylist 900 of the IM sender when the IM sender rolls a mouse pointer overthe name of the buddy 925 a, 925 b, 925 c, 925 d or otherwise specifiesa buddy in the buddy list 900. In another implementation, the IM sendermay tie their wallpaper or other personalization item setting to followthat of a selected buddy on the buddy list 900. In other words, thewallpaper of the IM sender may be set to follow that of a selectedbuddy, for example buddy 925 a, such that when buddy 925 a makes achange to the wallpaper or other personalization item, the resultingchange is reflected to the IM sender in the personalization itemsrendered for the IM sender.

IM personalization items of the IM recipient may be rendered by any typeof hardware, software, device, computer, computer system, equipment,component, program, application, code, storage medium, or propagatedsignal. In one implementation, the IM personalization items may berendered in a client/host context, and the IM personalization items maybe accessed or updated through a remote device in a client/hostenvironment. In another implementation, the IM personalization items maybe implemented in a standalone or offline client context. The IMpersonalization items may be rendered by the standalone/offline deviceand may be accessed or updated through a remote device in anon-client/host environment such as, for example, a LAN (Local AreaNetwork) server serving an end user or a mainframe serving a terminaldevice.

Regarding FIG. 10, procedure 1000 shows one possible implementation ofrendering a personalization item associated with the selected IMrecipient (step 520), as described with respect to FIG. 5. In procedure1000, personalization items of the selected IM recipient may be madeavailable to the IM sender system and rendered at the IM sender systembased on identifiers corresponding to the personalization items of theIM recipient, which may be maintained or accessed by the IM host system310.

In procedure 1000, the IM sender system 105 first sends the identifiercorresponding to the personalization item to the IM host system 310(step 1025). The identifiers may be associated with a screen name orother identifying information of the IM recipient. For example, theidentifiers may be associated with the screen name of the IM recipientand stored locally at the IM sender system, or the IM sender system mayretrieve the identifiers associated with the screen name of the IMrecipient from another location, such as the IM host system or anotherremotely-accessible data store.

The IM host system 310 receives the identifier from the IM sender system105 (step 1030).

Next, the IM host system 310 looks up the personalization item(s)associated with the identifier (step 1035), and retrieves thepersonalization item(s) corresponding to the identifier (step 1040). Inother words, the IM sender system uses the identifier to determine ifthe corresponding personalization item is available locally at the IMsender system, and if so, the IM sender system retrieves thecorresponding personalization item. When the personalization item is notavailable locally at the IM sender system, the IM sender system 105requests the personalization item by sending the selected identifier tothe IM host system 310 or another remotely-accessible data store (notshown). Alternatively, the personalization item itself may be associatedwith the IM recipient and retrieved by the IM sender system 105.

Ultimately, the personalization item(s) are returned to the IM sendersystem 105 (step 1045).

The corresponding personalization item(s) are received by the IM sendersystem 105 (step 1050). Receiving the corresponding personalization itemmay include saving (e.g., caching) the personalization item in a memoryor other storage at the local IM sender system 105.

Finally, the IM UI is populated with the personalization item(s) (step1055). That is, once the IM sender system locates or receives thepersonalization item, the IM sender system renders the item forperception by the IM sender. As shown with respect to FIG. 7, thepersonalization items to be populated may include a buddy icon 709 or IMwallpaper 707.

The relative order of steps 505-530 with respect to other steps inprocedure 500, and the relative order of steps 1025-1055 with respect toother steps in procedure 1000, and also with respect to each other, mayvary. Also, certain steps may be omitted entirely, as appropriate.

FIGS. 11 and 12 show one possible implementation of the proceduresdiscussed with respect to FIGS. 5 and 10. The IM sender system 105 andthe IM host system 310 interact according to exemplary procedures 1100and 1200 to make a personalization item selected by the IM recipientperceivable to the IM sender during an instant messaging communicationssession. FIGS. 11 and 12 differ from FIGS. 5 and 10 in thatpersonalization items are made available in response to a triggeringevent (e.g., a detected change in presence of a user being monitored)rather than in response to invocation of an application or applicationinterface.

Referring to FIG. 11, in the procedure 1100, the IM sender system 105and the IM host system 310 are physically and/or logically connected(step 1105). For instance, IM sender system 105 may connect to the IMhost system 310 across a network (e.g., network 160) by supplying an IMsender identification and password to a server (e.g., a login server) inorder to obtain access to the IM host system 310.

Next, the presence state or presence state change of the IM recipientsystem 305, e.g., login state, is detected by the IM host system 310(step 1108). The IM host system 310 may detect presence states or statechanges, such as, for example, when the IM recipient signs out, isinactive for a period of time, becomes active after having been inactivefor a period of time, indicates an ability to receive instant messages,or indicates an inability to receive instant messages. A pool ofpotential IM recipients may be monitored and associated with the screenname of a sender through use of a buddy list or similar mechanism.Alternatively, the entire user base may be monitored or some intelligentmethod of monitoring potential IM recipients may be used. The IM sendermay select one or more IM recipient to whom the IM sender may wish tosend an instant message.

After detecting the presence state or state change of the IM recipientsystem 305, the IM host system 310 may send or otherwise make accessibleto the IM sender system 105 and other IM systems a notification of theIM recipient presence state change or state change (step 1114). Sendingnotification of the presence state change may include sending anidentifier corresponding to a personalization item selected by the IMrecipient system 305. For example, the IM host system 310 may send anidentifier corresponding to a sound chosen by the IM recipient for thepresence state change.

In one implementation, the IM host system 310 assigns an identifier tothe personalization item. In another implementation, the IM recipientsystem 305 assigns the identifier to the personalization item. In yetanother implementation, the identifier is assigned by a host systemother than the IM host system 310.

The identifier typically includes information allowing the correspondingpersonalization item to be located and retrieved. For example, theidentifier may include a location of the personalization item. Theidentifier also may include a type identifier that identifies thepersonalization item as, for example, an icon, an IM wallpaper, anemoticon, or a sound. The type identifier also may include a file formatof the personalization item. Also, the identifier may include one ormore flags to indicate, for example, if the personalization item is acustom item or an “official” item, has been banned, or has expired.Another flag may redirect the sender to a different personalizationitem. The identifier may further include information concerning the sizeof the personalization item. The identifier may be in a predeterminedformat and may be of a predetermined length.

The IM sender system 105 receives the notification from the IM hostsystem 310 (step 1116). In the above example, receiving the notificationmay include receiving an identifier corresponding to a personalizationitem selected by the IM recipient system 305.

Next, the IM sender system 105 determines whether the correspondingpersonalization item is locally available (step 1118). For example, theIM sender system 105 may have stored the personalization in a localmemory or another local storage location. The IM sender system uses theidentifier to determine whether the corresponding personalization itemis locally available. For instance, the identifier may contain thelocation at which the corresponding personalization item is stored.

If the corresponding personalization item is available locally, the IMsender system retrieves the corresponding personalization item (step1120) and renders the personalization item (step 1130).

Otherwise, if the corresponding personalization item is not availablelocally, the IM sender system 105 requests the correspondingpersonalization item from the IM host system 310 or a location otherwisespecified by or inferred from the identifier (step 1122). That is, theIM sender system 105 may request the corresponding personalization itemfrom another location such as the IM recipient system 305 or a remote,third party server. Requesting the corresponding personalization itemmay include sending the identifier associated with the personalizationitem to the IM host system 310 along with a request to download thepersonalization item to the IM sender system 105.

When the IM host system 310 receives the request for a personalizationitem from the IM sender system (step 1124), the IM host system 310provides the corresponding personalization item to the IM sender system(step 1126). Receiving the request may include having the IM host system310 receive the identifier associated with the personalization itemalong with a request to download the personalization item to the IMsender system 105.

Next, the corresponding personalization item is received by the IMsender system (step 1128), which may save the personalization item in amemory or other storage at the local IM sender system 105. Then, thepersonalization item is rendered (step 1130). For example, as discussedwith respect to FIG. 9, the personalization items may includepersonalization items for a buddy list UI 900.

Referring to FIG. 12, in procedure 1200, an instant message applicationis opened by the IM sender system 105 (step 1235), in a similar mannerto that discussed with respect to step 505 of FIG. 5. The IM sender mayalso open an IM UI, such as the UI 700 shown in FIG. 7 and select anintended destination recipient, as discussed above with respect to steps510 and 515 of FIG. 5. In one implementation, rather than relying on amechanism such as a buddy list or a state change to identify users forwhich personalization items will be made available, a mechanismidentifies the users for which personalization items will be madeavailable based on users selected by the IM senders for communications.

To make the personalization items of the IM recipient (for examplepersonalization items 707 and 709) available to the IM sender (forexample, in UI 700), the IM sender system 105 selects the identifierscorresponding to the personalization items (for example, 707 and 709) ofthe IM recipient. The identifiers may be associated with a screen nameor other identifying information of the IM recipient. As such,personalization items of the IM recipient may be made available to theIM sender before the receipt by the IM sender of an IM from the IMrecipient.

The IM sender system 105 uses the identifiers to identify thepersonalization item associated with the recipient, and to locateperceivable content corresponding to the identifier.

Because various aspects of steps 1236-1250 are similar to thosediscussed above with respect to steps 1116-1130 of procedure 1100, thefollowing discussion of steps 1236-1250 is somewhat abbreviated.

The IM sender system 105 obtains an identifier from the IM host system310 (step 1236) corresponding to the personalization item selected bythe IM sender system 105, as discussed above with respect to step 1116.

Next, the IM sender system 105 determines whether the correspondingpersonalization item is available locally (step 1238). As discussedabove with respect to step 1118, the IM sender system 105 may havestored the personalization in a local memory or other local storagelocation. The IM sender system 105 uses the identifier to determinewhether the corresponding personalization is available locally. Forinstance, the identifier may contain the location at which thecorresponding personalization item is stored.

If the corresponding personalization item is available locally, the IMsender system 105 retrieves the corresponding personalization item (step1240) and the personalization item is rendered (step 1250).

Otherwise, if the corresponding personalization item is not availablelocally, the IM sender system 105 requests the correspondingpersonalization item from the IM host system 310 (step 1242).Alternatively, as discussed above with respect to step 1122, the IMsender system 105 may request the corresponding personalization itemfrom another location. In one implementation, the personalization itemmay be provided by a third party, and may be made available inconsideration of a payment by the IM sender or the IM recipient.Requesting the corresponding personalization item may include sending tothe IM host system 310 the identifier associated with thepersonalization item along with a request to download thepersonalization item to the IM sender system 105.

The IM host system 310 receives the request for the personalization itemfrom the IM sender system 105 (step 1244). As discussed above withrespect to step 1124, receiving the request may include receiving theidentifier associated with the personalization item along with a requestto download the personalization item to the IM sender system 105. The IMhost system 310 provides the corresponding personalization item to theIM sender system 105 (step 1246).

The corresponding personalization item is received by the IM sendersystem 105 (step 1248). As discussed above with respect to step 1128,receiving the corresponding personalization item may include saving thepersonalization item in a memory or other storage at the local IM sendersystem 105.

Finally, the personalization item is rendered (step 1250). As discussedwith respect to FIG. 7, the personalization item to be rendered mayinclude a buddy icon 709 or IM wallpaper 707.

The relative order of steps 1105-1130 with respect to other steps inprocedure 1100, and the relative order of steps 1235-1250 with respectto other steps in procedure 1200, and also with respect to each other,may vary. Also, certain steps may be omitted entirely, as appropriate.For example, referring to FIG. 11, if the IM recipient has not chosen apersonalization item to be sent to the IM sender system 105 upon apresence state change, then no such item will be sent and steps1116-1130 may be eliminated entirely.

In one implementation, a buddy icon of an IM recipient may be shown in abuddy list, or other personalization items of an IM recipient may beshown in a buddy list.

In another implementation, the IM recipient and/or the IM sender pay asubscription fee to access/use certain personalization items, and thepersonalization items may be provided by a third party such as a serverother than the IM host 310. In another implementation, thepersonalization items expire and must be replaced after a predeterminedevent such as a predetermined length of time, passage of a predetermineddate, or a predetermined number of uses. Also, a personalization itemmay be banned if, for example, it is deemed to be offensive,inappropriate, or to otherwise violate a term of service agreement. Ifit is determined that the personalization item is expired or banned,display of such a personalization item will be disallowed and the usertypically will be required to choose a different personalization item.

Other implementations are within the scope of the following claims. Forexample, one identifier could correspond to a group of personalizationitems, or a personalization item could have more than one identifier. Asa further example, although the examples above are given in an instantmessage context, other communications systems with similar attributesmay be used. For example, personalization items may be used in a chatroom or in e-mail communications. Also, the user interface may be aviewable interface, an audible interface, a tactile interface, or anycombination of these.

1-40. (canceled)
 41. A computer-implemented method comprising: receivingselection of an intended instant message recipient from a plurality ofpotential instant message recipients; identifying a firstpersonalization item associated with the intended instant messagerecipient, the first personalization item being specific to a presencestate of the intended instant message recipient; and rendering, in auser interface of an instant messaging application associated with aninstant message sender: the first personalization item; a secondpersonalization item of the instant message sender; and instant messagetext exchanged between the intended instant message recipient and theinstant message sender wherein the rendering includes rendering thefirst personalization item, the second personalization item, and theinstant message text within a separate display area, without rendering,in the separate display area, names of other potential instant messagerecipients in the plurality of instant message recipients.
 42. Themethod of claim 41, wherein the rendering includes displaying an inputtext field for inputting a text message by the instant message senderfor delivery to the intended instant message recipient in an instantmessage, and wherein the rendering causes the first personalization itemand the input text field to be displayed to the instant message senderprior to communication with the intended instant message recipient. 43.The method of claim 41 further comprising causing the first and secondpersonalization items to be stored on a host system.
 44. The method ofclaim 41 wherein identifying the first personalization item comprisescausing the first personalization item to be accessed on a host system.45. The method of claim 44 further comprising receiving the first andsecond personalization items from the host system.
 46. The method ofclaim 41 wherein the first and second personalization items are renderedprior to communication of an instant message between the instant messagesender and the intended instant message recipient.
 47. The method ofclaim 41 wherein the first and second personalization items are renderedbefore a communications session is established between the instantmessage sender and the intended instant message recipient.
 48. Themethod of claim 41 wherein the first and second personalization itemsare rendered before the instant message sender sends a message to theintended instant message recipient.
 49. The method of claim 41 whereinthe first and second personalization items are rendered before theinstant message sender receives a message from the intended instantmessage recipient.
 50. The method of claim 41, further comprising:receiving identities of the potential instant message recipients; andaccessing an identifier associated with each of the individual potentialinstant message recipients based upon the received identity, wherein thefirst personalization item is identified based on an identifierassociated with the intended instant message recipient.
 51. The methodof claim 41 further comprising accessing a user identifier for theintended instant message recipient, wherein the identifier provides alocation of the first personalization item.
 52. The method of claim 51wherein the location of the first personalization item comprises alocation on a host system.
 53. A computer readable storage mediumincluding instructions that, when executed by a processor, perform amethod for enabling perception of a personalization item associated withan instant messaging communications session, the method comprising:receiving selection of an intended instant message recipient from aplurality of potential instant message recipients; identifying a firstpersonalization item associated with the intended instant messagerecipient, the first personalization item being specific to a presencestate of the intended instant message recipient; and rendering, in auser interface of an instant messaging application associated with aninstant message sender: the first personalization item; a secondpersonalization item of the instant message sender; and instant messagetext exchanged between the intended instant message recipient and theinstant message sender wherein the rendering includes rendering thefirst personalization item, the second personalization item, and theinstant message text within a separate display area, without rendering,in the separate display area, names of other potential instant messagerecipients in the plurality of instant message recipients.
 54. Thecomputer readable storage medium of claim 53, wherein the renderingincludes displaying an input text field for inputting a text message bythe instant message sender for delivery to the intended instant messagerecipient in an instant message, and wherein the rendering causes thefirst personalization item and the input text field to be displayed tothe instant message sender prior to communication with the intendedinstant message recipient.
 55. The computer readable storage medium ofclaim 53 wherein the first and second personalization items are renderedbefore the instant message sender sends a message to the intendedinstant message recipient.
 56. The computer readable storage medium ofclaim 53 further comprising, prior to identifying the firstpersonalization item, accessing a user identifier for the intendedinstant message recipient, wherein the identifier provides a location ofthe first personalization item, and wherein the location of the firstpersonalization item comprises a location on a host system.
 57. A systemfor enabling perception of a personalization item associated with aninstant messaging communications session comprising: at least oneprocessor; a memory communicatively coupled to the at least oneprocessor and including instructions that, when executed by the at leastone processor, perform a method, the method comprising: receivingselection of an intended instant message recipient from a plurality ofpotential instant message recipients; identifying a firstpersonalization item associated with the intended instant messagerecipient, the first personalization item being specific to a presencestate of the intended instant message recipient; and rendering, in auser interface of an instant messaging application associated with aninstant message sender: the first personalization item; a secondpersonalization item of the instant message sender; and instant messagetext exchanged between the intended instant message recipient and theinstant message sender wherein the rendering includes rendering thefirst personalization item, the second personalization item, and theinstant message text within a separate display area, without rendering,in the separate display area, names of other potential instant messagerecipients in the plurality of instant message recipients.
 58. Thesystem of claim 57, wherein the rendering includes displaying an inputtext field for inputting a text message by the instant message senderfor delivery to the intended instant message recipient in an instantmessage, and wherein the rendering causes the first personalization itemand the input text field to be displayed to the instant message senderprior to communication with the intended instant message recipient. 59.The system of claim 57 wherein the first and second personalizationitems are rendered before the instant message sender sends a message tothe intended instant message recipient.
 60. The system of claim 57, themethod further comprising, prior to identifying the firstpersonalization item, accessing a user identifier for the intendedinstant message recipient, wherein the identifier provides a location ofthe first personalization item, and wherein the location of the firstpersonalization item comprises a location on a host system.